Fix #619 fix login #629

Anchel123 · 2025-01-26T10:13:25Z

PR Type

Enhancement, Bug fix

Description

Replaced LandingPage gradient background with Gradient class.
Improved Dropzone interaction by adding cursor styles.
Updated Home page to display logo, version, and copyright.
Simplified and adjusted layout and styling across components.

Changes walkthrough 📝

Relevant files

Enhancement

Header.tsx `Updated background styling in Header component` app/components/Header.tsx Replaced `Top` class with `Gradient` for background styling.	+1/-1
Dropzone.tsx `Enhanced Dropzone interaction and styling` app/components/ui/Dropzone.tsx Enhanced `Dropzone` interaction by adding cursor styles. Improved disabled state styling for better UX.	+1/-1
layout.tsx `Updated body background styling in layout` app/layout.tsx Replaced `LandingPage` class with `bg-foreground` for body styling.	+1/-1
LoginForm.tsx `Simplified LoginForm layout and updated styling` app/login/LoginForm.tsx Removed redundant `bg-foreground` wrapper. Replaced `Top` class with `Gradient` for background styling.	+3/-5
page.tsx `Updated Home page with logo and version details` app/page.tsx Added logo display using `Image` component. Displayed app version and copyright information. Replaced `LandingPage` class with `bg-foreground`.	+11/-3
globals.css `Refactored global CSS for background gradients` app/globals.css Removed `LandingPage` gradient background definition. Renamed `Top` class to `Gradient` for consistency.	+1/-5

Need help?
Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
Check out the documentation for more information.

vercel · 2025-01-26T10:13:30Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
falkordb-browser	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 28, 2025 7:25pm

coderabbitai · 2025-01-26T10:13:32Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

qodo-merge-pro · 2025-01-26T10:13:46Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review Version Display The version display uses a template literal with curly braces that may not render correctly: `{${pkg.version}}`. Consider using just `${pkg.version}` instead. <p>Version: {`{${pkg.version}}`}</p> Copyright Year The copyright year range starts from 2024 hardcoded, which may become outdated. Consider using dynamic start year or just the current year. <p className="text-sm">All Rights Reserved © 2024 - {new Date().getFullYear()} falkordb.com</p>

qodo-merge-pro · 2025-01-26T10:14:01Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Fix version string template syntax The version string template literal contains invalid syntax. Remove the curly braces around pkg.version to properly display the version number. app/page.tsx [15] -<p>Version: {`{${pkg.version}}`}</p> +<p>Version: {pkg.version}</p> Apply this suggestion Suggestion importance[1-10]: 8 Why: The current version string syntax is incorrect and would display literal curly braces. Fixing this is important as it affects the display of version information to users.	8
General	Improve disabled state accessibility The disabled state cursor style should be 'not-allowed' instead of 'text' to better indicate interaction restrictions following accessibility best practices. app/components/ui/Dropzone.tsx [59] -<p className={cn('underline underline-offset-2 text-[#99E4E5]', disabled ? "opacity-30 cursor-text" : "cursor-pointer")}>Upload Certificate</p> +<p className={cn('underline underline-offset-2 text-[#99E4E5]', disabled ? "opacity-30 cursor-not-allowed" : "cursor-pointer")}>Upload Certificate</p> Apply this suggestion Suggestion importance[1-10]: 7 Why: Using 'cursor-not-allowed' instead of 'cursor-text' follows accessibility best practices and provides better visual feedback for disabled elements.	7

qodo-merge-pro · 2025-01-26T10:22:12Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: test
Failed stage: Run Playwright tests with detailed reporting [❌]
Failed test name: settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries
Failure summary: The test failed in the Settings Tests section while trying to modify the MAX_INFO_QUERIES setting via UI validation API. Specifically: Test case "@admin Modify MAX_INFO_QUERIES via UI validation via API" failed for both Chromium and Firefox browsers The failure occurred at line 123 in settingsConfig.spec.ts where the actual value did not match the expected value The test was attempting to set MAX_INFO_QUERIES to "20" but the validation check failed The test retried 3 times but failed consistently with the same error
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1539: - Network: http://10.1.0.11:3000 1540: ✓ Starting... 1541: ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. 1542: ✓ Ready in 347ms 1543: Running 191 tests using 1 worker 1544: Running 191 tests using 1 worker 1545: [next-auth][warn][NEXTAUTH_URL] 1546: https://next-auth.js.org/warnings#nextauth_url 1547: TypeError: Cannot read properties of null (reading '1') 1548: at t.transformReply (.next/server/chunks/488.js:1:90312) 1549: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1550: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1551: at async p (.next/server/app/api/user/route.js:1:2243) 1552: TypeError: Cannot read properties of null (reading '1') 1553: at t.transformReply (.next/server/chunks/488.js:1:90312) 1554: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1555: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1556: at async p (.next/server/app/api/user/route.js:1:2243) 1557: · ✓ 1 [setup] › auth.setup.ts:12:6 › admin authentication (6.1s) 1558: [Error: NOPERM User readwriteuser has no permissions to run the 'acl\|getuser' command] 1559: [Error: ERR wrong number of arguments for 'graph.QUERY' command] 1560: · ✓ 2 [setup] › auth.setup.ts:36:10 › readwrite authentication (1.9s) 1561: [Error: NOPERM User readonlyuser has no permissions to run the 'acl\|getuser' command] 1562: [Error: NOPERM User readonlyuser has no permissions to run the 'graph.QUERY' command] ... 1566: · ✓ 6 [[Admin] Chromium] › graph.spec.ts:50:13 › Graph Tests › @admin Create graph -> click the Export Data button -> verify the file has been successfully downloaded (1.3s) 1567: · ✓ 7 [[Admin] Chromium] › graph.spec.ts:61:13 › Graph Tests › @admin Query Test: Create a graph via api -> run a query via api and validate that the response data is correct (23ms) 1568: · ✓ 8 [[Admin] Chromium] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.6s) 1569: · ✓ 9 [[Admin] Chromium] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.1s) 1570: · ✓ 10 [[Admin] Chromium] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s) 1571: · ✓ 11 [[Admin] Chromium] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.1s) 1572: · ✓ 12 [[Admin] Chromium] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.2s) 1573: · ✓ 13 [[Admin] Chromium] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.1s) 1574: [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN] 1575: · ✓ 14 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: aa description: invalid input - character (2.4s) 1576: [Error: Failed to set config value MAX_QUEUED_QUERIES to -3] 1577: · ✓ 15 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: -3 description: invalid input - negative number (2.2s) 1578: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1579: · ✓ 16 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 00-1 description: invalid input (2.2s) 1580: · ✓ 17 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 1 description: valid input (2.2s) 1581: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1582: · ✓ 18 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 0 description: invalid input - zero value (2.2s) 1583: [Error: Failed to set config value TIMEOUT_MAX to NaN] 1584: · ✓ 19 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1585: [Error: Failed to set config value TIMEOUT_MAX to -3] 1586: · ✓ 20 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1587: · ✓ 21 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1588: · ✓ 22 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 30 description: valid input (1.2s) 1589: [Error: Failed to set config value TIMEOUT_DEFAULT to NaN] 1590: · ✓ 23 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1591: [Error: Failed to set config value TIMEOUT_DEFAULT to -3] 1592: · ✓ 24 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1593: · ✓ 25 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1594: · ✓ 26 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 1 description: valid input (1.2s) 1595: · ✓ 27 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1596: [Error: Failed to set config value RESULTSET_SIZE to NaN] 1597: · ✓ 28 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1598: · ✓ 29 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1599: · ✓ 30 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1600: · ✓ 31 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 1 description: valid input (1.2s) 1601: · ✓ 32 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1602: [Error: Failed to set config value QUERY_MEM_CAPACITY to NaN] 1603: · ✓ 33 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1604: [Error: Failed to set config value QUERY_MEM_CAPACITY to -3] 1605: · ✓ 34 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1606: · ✓ 35 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1607: · ✓ 36 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 1 description: valid input (1.2s) 1608: · ✓ 37 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1609: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to NaN] 1610: · ✓ 38 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1611: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to -3] 1612: · ✓ 39 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1613: · ✓ 40 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1614: · ✓ 41 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 1 description: valid input (1.2s) 1615: · ✓ 42 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1616: [Error: Failed to set config value CMD_INFO to aa] 1617: · ✓ 43 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1618: [Error: Failed to set config value CMD_INFO to -3] 1619: · ✓ 44 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1620: [Error: Failed to set config value CMD_INFO to 00-1] 1621: · ✓ 45 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1622: [Error: Failed to set config value CMD_INFO to 10s] 1623: · ✓ 46 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 10s description: invalid input (1.2s) 1624: · ✓ 47 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: no description: valid input - no value (1.2s) 1625: · ✓ 48 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: yes description: valid input - yes value (1.2s) 1626: [Error: Failed to set config value MAX_INFO_QUERIES to NaN] 1627: · ✓ 49 [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1628: [Error: Failed to set config value MAX_INFO_QUERIES to -3] ... 1635: · ✓ 56 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (735ms) 1636: · ✓ 57 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (710ms) 1637: · ✓ 58 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via UI validation via API: Input value: 20 description: modify queryMemCapacity (734ms) 1638: · ✓ 59 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via UI validation via API: Input value: 20 description: modify vKeyMaxEntityCount (730ms) 1639: · ✓ 60 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (714ms) 1640: × ✘ 61 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (719ms) 1641: × ✘ 62 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #1) (1.1s) 1642: F ✘ 63 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #2) (1.0s) 1643: TypeError: Cannot read properties of null (reading '1') 1644: at t.transformReply (.next/server/chunks/488.js:1:90312) 1645: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1646: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1647: at async p (.next/server/app/api/user/route.js:1:2243) 1648: · ✓ 64 [[Admin] Chromium] › settingsUsers.spec.ts:19:9 › Settings Tests › @admin Add one new user -> validating user exists in the users list (2.8s) 1649: TypeError: Cannot read properties of null (reading '1') 1650: at t.transformReply (.next/server/chunks/488.js:1:90312) 1651: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1652: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1653: at async p (.next/server/app/api/user/route.js:1:2243) 1654: · ✓ 65 [[Admin] Chromium] › settingsUsers.spec.ts:29:9 › Settings Tests › @admin Add one user -> remove one user -> Validate that the user has been removed (3.1s) 1655: TypeError: Cannot read properties of null (reading '1') 1656: at t.transformReply (.next/server/chunks/488.js:1:90312) 1657: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1658: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1659: at async p (.next/server/app/api/user/route.js:1:2243) 1660: · ✓ 66 [[Admin] Chromium] › settingsUsers.spec.ts:44:9 › Settings Tests › @admin Add one user -> change the role -> Validate that the user role have been changed (4.0s) 1661: TypeError: Cannot read properties of null (reading '1') 1662: at t.transformReply (.next/server/chunks/488.js:1:90312) 1663: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1664: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1665: at async p (.next/server/app/api/user/route.js:1:2243) 1666: TypeError: Cannot read properties of null (reading '1') 1667: at t.transformReply (.next/server/chunks/488.js:1:90312) 1668: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1669: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1670: at async p (.next/server/app/api/user/route.js:1:2243) 1671: · ✓ 67 [[Admin] Chromium] › settingsUsers.spec.ts:59:9 › Settings Tests › @admin Add two users -> change their roles via checkbox -> Validate that the users roles have been changed (6.5s) 1672: TypeError: Cannot read properties of null (reading '1') 1673: at t.transformReply (.next/server/chunks/488.js:1:90312) 1674: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1675: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1676: at async p (.next/server/app/api/user/route.js:1:2243) 1677: TypeError: Cannot read properties of null (reading '1') ... 1682: · ✓ 68 [[Admin] Chromium] › settingsUsers.spec.ts:80:9 › Settings Tests › @admin Add two users -> delete the two users by checkbox -> Validate that the users have been deleted (6.3s) 1683: · ✓ 69 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password (3.0s) 1684: · ✓ 70 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character (2.9s) 1685: · ✓ 71 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits (2.9s) 1686: · ✓ 72 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters (3.0s) 1687: · ✓ 73 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters (3.0s) 1688: · ✓ 74 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: reason: without password (3.0s) 1689: · ✓ 75 [[Admin] Chromium] › settingsUsers.spec.ts:121:9 › Settings Tests › @admin Attempt to add a user without assigning a role -> Verify that the user has not been added (2.9s) 1690: [Error: ERR The 'default' user cannot be removed] 1691: · ✓ 76 [[Admin] Chromium] › settingsUsers.spec.ts:132:9 › Settings Tests › @admin Attempt to delete the default admin user -> Verify that the user has not been deleted. (770ms) 1692: TypeError: Cannot read properties of null (reading '1') 1693: at t.transformReply (.next/server/chunks/488.js:1:90312) 1694: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1695: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1696: at async p (.next/server/app/api/user/route.js:1:2243) 1697: Error: Missing parameters 1698: at p (.next/server/app/api/user/route.js:1:2208) 1699: · ✓ 77 [[Admin] Chromium] › settingsUsers.spec.ts:140:9 › Settings Tests › @admin API Test:Add user via API -> Validated user existing via API -> Delete user via API. (38ms) 1700: Error: Missing parameters 1701: at p (.next/server/app/api/user/route.js:1:2208) 1702: · ✓ 78 [[Admin] Chromium] › settingsUsers.spec.ts:150:9 › Settings Tests › @admin API Test: without passing a username, Attempt to add a user and validate the user was not added (14ms) 1703: Error: Missing parameters 1704: at p (.next/server/app/api/user/route.js:1:2208) 1705: · ✓ 79 [[Admin] Chromium] › settingsUsers.spec.ts:159:9 › Settings Tests › @admin API Test: without passing a role, Attempt to add a user and validate the user was not added (13ms) 1706: Error: Missing parameters ... 1712: · ✓ 84 [[Admin] Firefox] › graph.spec.ts:50:13 › Graph Tests › @admin Create graph -> click the Export Data button -> verify the file has been successfully downloaded (1.3s) 1713: · ✓ 85 [[Admin] Firefox] › graph.spec.ts:61:13 › Graph Tests › @admin Query Test: Create a graph via api -> run a query via api and validate that the response data is correct (25ms) 1714: · ✓ 86 [[Admin] Firefox] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.6s) 1715: · ✓ 87 [[Admin] Firefox] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.2s) 1716: · ✓ 88 [[Admin] Firefox] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s) 1717: · ✓ 89 [[Admin] Firefox] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.2s) 1718: · ✓ 90 [[Admin] Firefox] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.3s) 1719: · ✓ 91 [[Admin] Firefox] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.1s) 1720: [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN] 1721: · ✓ 92 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: aa description: invalid input - character (2.4s) 1722: [Error: Failed to set config value MAX_QUEUED_QUERIES to -3] 1723: · ✓ 93 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: -3 description: invalid input - negative number (2.2s) 1724: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1725: · ✓ 94 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 00-1 description: invalid input (2.2s) 1726: · ✓ 95 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 1 description: valid input (2.2s) 1727: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1728: · ✓ 96 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 0 description: invalid input - zero value (2.2s) 1729: [Error: Failed to set config value TIMEOUT_MAX to NaN] 1730: · ✓ 97 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1731: [Error: Failed to set config value TIMEOUT_MAX to -3] 1732: · ✓ 98 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1733: · ✓ 99 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1734: · ✓ 100 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 30 description: valid input (1.2s) 1735: [Error: Failed to set config value TIMEOUT_DEFAULT to NaN] 1736: · ✓ 101 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1737: [Error: Failed to set config value TIMEOUT_DEFAULT to -3] 1738: · ✓ 102 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1739: · ✓ 103 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1740: · ✓ 104 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 1 description: valid input (1.2s) 1741: · ✓ 105 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1742: [Error: Failed to set config value RESULTSET_SIZE to NaN] 1743: · ✓ 106 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1744: · ✓ 107 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1745: · ✓ 108 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1746: · ✓ 109 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 1 description: valid input (1.2s) 1747: · ✓ 110 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1748: [Error: Failed to set config value QUERY_MEM_CAPACITY to NaN] 1749: · ✓ 111 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1750: [Error: Failed to set config value QUERY_MEM_CAPACITY to -3] 1751: · ✓ 112 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1752: · ✓ 113 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1753: · ✓ 114 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 1 description: valid input (1.2s) 1754: · ✓ 115 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1755: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to NaN] 1756: · ✓ 116 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1757: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to -3] 1758: · ✓ 117 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1759: · ✓ 118 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1760: · ✓ 119 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 1 description: valid input (1.2s) 1761: · ✓ 120 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1762: [Error: Failed to set config value CMD_INFO to aa] 1763: · ✓ 121 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1764: [Error: Failed to set config value CMD_INFO to -3] 1765: · ✓ 122 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1766: [Error: Failed to set config value CMD_INFO to 00-1] 1767: · ✓ 123 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1768: [Error: Failed to set config value CMD_INFO to 10s] 1769: · ✓ 124 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 10s description: invalid input (1.2s) 1770: · ✓ 125 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: no description: valid input - no value (1.2s) 1771: · ✓ 126 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: yes description: valid input - yes value (1.2s) 1772: [Error: Failed to set config value MAX_INFO_QUERIES to NaN] 1773: · ✓ 127 [[Admin] Firefox] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1774: [Error: Failed to set config value MAX_INFO_QUERIES to -3] ... 1781: · ✓ 134 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (732ms) 1782: · ✓ 135 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (712ms) 1783: · ✓ 136 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via UI validation via API: Input value: 20 description: modify queryMemCapacity (748ms) 1784: · ✓ 137 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via UI validation via API: Input value: 20 description: modify vKeyMaxEntityCount (732ms) 1785: · ✓ 138 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (715ms) 1786: × ✘ 139 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (715ms) 1787: × ✘ 140 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #1) (1.1s) 1788: F ✘ 141 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #2) (1.0s) 1789: TypeError: Cannot read properties of null (reading '1') 1790: at t.transformReply (.next/server/chunks/488.js:1:90312) 1791: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1792: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1793: at async p (.next/server/app/api/user/route.js:1:2243) 1794: · ✓ 142 [[Admin] Firefox] › settingsUsers.spec.ts:19:9 › Settings Tests › @admin Add one new user -> validating user exists in the users list (2.8s) 1795: TypeError: Cannot read properties of null (reading '1') 1796: at t.transformReply (.next/server/chunks/488.js:1:90312) 1797: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1798: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1799: at async p (.next/server/app/api/user/route.js:1:2243) 1800: · ✓ 143 [[Admin] Firefox] › settingsUsers.spec.ts:29:9 › Settings Tests › @admin Add one user -> remove one user -> Validate that the user has been removed (3.1s) 1801: TypeError: Cannot read properties of null (reading '1') 1802: at t.transformReply (.next/server/chunks/488.js:1:90312) 1803: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1804: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1805: at async p (.next/server/app/api/user/route.js:1:2243) 1806: · ✓ 144 [[Admin] Firefox] › settingsUsers.spec.ts:44:9 › Settings Tests › @admin Add one user -> change the role -> Validate that the user role have been changed (4.0s) 1807: TypeError: Cannot read properties of null (reading '1') 1808: at t.transformReply (.next/server/chunks/488.js:1:90312) 1809: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1810: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1811: at async p (.next/server/app/api/user/route.js:1:2243) 1812: TypeError: Cannot read properties of null (reading '1') 1813: at t.transformReply (.next/server/chunks/488.js:1:90312) 1814: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1815: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1816: at async p (.next/server/app/api/user/route.js:1:2243) 1817: · ✓ 145 [[Admin] Firefox] › settingsUsers.spec.ts:59:9 › Settings Tests › @admin Add two users -> change their roles via checkbox -> Validate that the users roles have been changed (6.5s) 1818: TypeError: Cannot read properties of null (reading '1') 1819: at t.transformReply (.next/server/chunks/488.js:1:90312) 1820: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1821: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1822: at async p (.next/server/app/api/user/route.js:1:2243) 1823: TypeError: Cannot read properties of null (reading '1') ... 1828: · ✓ 146 [[Admin] Firefox] › settingsUsers.spec.ts:80:9 › Settings Tests › @admin Add two users -> delete the two users by checkbox -> Validate that the users have been deleted (6.3s) 1829: · ✓ 147 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password (3.0s) 1830: · ✓ 148 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character (2.9s) 1831: · ✓ 149 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits (2.9s) 1832: · ✓ 150 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters (2.9s) 1833: · ✓ 151 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters (3.0s) 1834: · ✓ 152 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: reason: without password (2.9s) 1835: · ✓ 153 [[Admin] Firefox] › settingsUsers.spec.ts:121:9 › Settings Tests › @admin Attempt to add a user without assigning a role -> Verify that the user has not been added (2.9s) 1836: [Error: ERR The 'default' user cannot be removed] 1837: · ✓ 154 [[Admin] Firefox] › settingsUsers.spec.ts:132:9 › Settings Tests › @admin Attempt to delete the default admin user -> Verify that the user has not been deleted. (770ms) 1838: TypeError: Cannot read properties of null (reading '1') 1839: at t.transformReply (.next/server/chunks/488.js:1:90312) 1840: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1841: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1842: at async p (.next/server/app/api/user/route.js:1:2243) 1843: Error: Missing parameters 1844: at p (.next/server/app/api/user/route.js:1:2208) 1845: · ✓ 155 [[Admin] Firefox] › settingsUsers.spec.ts:140:9 › Settings Tests › @admin API Test:Add user via API -> Validated user existing via API -> Delete user via API. (35ms) 1846: Error: Missing parameters 1847: at p (.next/server/app/api/user/route.js:1:2208) 1848: · ✓ 156 [[Admin] Firefox] › settingsUsers.spec.ts:150:9 › Settings Tests › @admin API Test: without passing a username, Attempt to add a user and validate the user was not added (14ms) 1849: Error: Missing parameters 1850: at p (.next/server/app/api/user/route.js:1:2208) 1851: · ✓ 157 [[Admin] Firefox] › settingsUsers.spec.ts:159:9 › Settings Tests › @admin API Test: without passing a role, Attempt to add a user and validate the user was not added (11ms) 1852: Error: Missing parameters ... 1885: · ✓ 189 [[Read-Only] - Firefox] › navBar.spec.ts:20:13 › Navbar tests › @readonly Verify clicking on FalkorDB logo redirects to specified URL (1.7s) 1886: · ✓ 190 [[Read-Only] - Firefox] › navBar.spec.ts:29:13 › Navbar tests › @readonly Verify clicking on Graphs button redirects to specified URL (1.1s) 1887: · ✓ 191 [[Read-Only] - Firefox] › navBar.spec.ts:39:13 › Navbar tests › @readonly Verify clicking on Schemas button redirects to specified URL (2.0s) 1888: · ✓ 192 [[Read-Only] - Firefox] › navBar.spec.ts:49:13 › Navbar tests › @readonly Verify clicking on help -> Documentation redirects to specified URL (1.1s) 1889: · ✓ 193 [[Read-Only] - Firefox] › navBar.spec.ts:58:13 › Navbar tests › @readonly Verify clicking on help -> Support redirects to specified URL (1.2s) 1890: · ✓ 194 [[Read-Only] - Firefox] › navBar.spec.ts:67:13 › Navbar tests › @readonly Verify clicking on Settings redirects to specified URL (1.0s) 1891: · ✓ 195 [[Read-Only] - Firefox] › signOut.spec.ts:19:13 › @readonly SignOut Test › Sign out Test (2.4s) 1892: 1) [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1893: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1897: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1898: > 123 \| expect(value === input).toBe(expected) 1899: \| ^ 1900: 124 \| }); 1901: 125 \| }) 1902: 126 \| 1903: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1904: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 1905: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1914: 126 \| 1915: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1916: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 1917: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 1918: Usage: 1919: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 1920: ──────────────────────────────────────────────────────────────────────────────────────────────── 1921: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 1922: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1926: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1927: > 123 \| expect(value === input).toBe(expected) 1928: \| ^ 1929: 124 \| }); 1930: 125 \| }) 1931: 126 \| 1932: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1933: 2) [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1934: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1938: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1939: > 123 \| expect(value === input).toBe(expected) 1940: \| ^ 1941: 124 \| }); 1942: 125 \| }) 1943: 126 \| 1944: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1945: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 1946: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1955: 126 \| 1956: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1957: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 1958: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 1959: Usage: 1960: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 1961: ──────────────────────────────────────────────────────────────────────────────────────────────── 1962: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 1963: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1969: \| ^ 1970: 124 \| }); 1971: 125 \| }) 1972: 126 \| 1973: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1974: Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.2s) 1975: Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.2s) 1976: Consider splitting slow test files to speed up parallel execution 1977: 2 failed 1978: [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1979: [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1980: 189 passed (5.5m) 1981: 1) [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1982: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1986: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1987: > 123 \| expect(value === input).toBe(expected) 1988: \| ^ 1989: 124 \| }); 1990: 125 \| }) 1991: 126 \| 1992: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1993: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 1994: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2003: 126 \| 2004: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2005: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 2006: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 2007: Usage: 2008: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 2009: ──────────────────────────────────────────────────────────────────────────────────────────────── 2010: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 2011: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2015: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2016: > 123 \| expect(value === input).toBe(expected) 2017: \| ^ 2018: 124 \| }); 2019: 125 \| }) 2020: 126 \| 2021: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2022: 2) [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2023: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2027: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2028: > 123 \| expect(value === input).toBe(expected) 2029: \| ^ 2030: 124 \| }); 2031: 125 \| }) 2032: 126 \| 2033: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2034: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 2035: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2044: 126 \| 2045: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2046: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 2047: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 2048: Usage: 2049: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 2050: ──────────────────────────────────────────────────────────────────────────────────────────────── 2051: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 2052: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2058: \| ^ 2059: 124 \| }); 2060: 125 \| }) 2061: 126 \| 2062: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2063: Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.2s) 2064: Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.2s) 2065: Consider splitting slow test files to speed up parallel execution 2066: 2 failed 2067: [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2068: [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2069: 189 passed (5.5m) 2070: ##[error]Process completed with exit code 1. ... 2088: [command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand 2089: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' \|\| :" 2090: [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader 2091: http.https://github.com/.extraheader 2092: [command]/usr/bin/git config --local --unset-all http.https://github.com/.extraheader 2093: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' \|\| :" 2094: Print service container logs: 9863cb9f19c84ea19c267e9cff7a3505_falkordbfalkordblatest_dde162 2095: ##[command]/usr/bin/docker logs --details 49aa517fe626b4a1614f98f507cfc609c0d68337fdfce462103670ca6ff8ca91 2096: 11:C 26 Jan 2025 10:14:16.878 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

Anchel123 added 2 commits January 23, 2025 14:36

change bg and display logo, version and copy rights

9bd266a

adjust the bg better and fix interaction with the dropzone

e509ef4

vercel bot deployed to Preview January 26, 2025 10:15 View deployment

Anchel123 linked an issue Jan 26, 2025 that may be closed by this pull request

Login button visibility and styling issue on login page #619

Open

Merge branch 'staging' into fix-login

25c6b30

vercel bot deployed to Preview January 28, 2025 19:25 View deployment

barakb approved these changes Jan 29, 2025

View reviewed changes

Anchel123 merged commit 63ae8ea into staging Jan 29, 2025
8 checks passed

Anchel123 deleted the fix-login branch January 29, 2025 10:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix #619 fix login #629

Fix #619 fix login #629

Anchel123 commented Jan 26, 2025 •

edited by qodo-merge-pro bot

Loading

vercel bot commented Jan 26, 2025 •

edited

Loading

coderabbitai bot commented Jan 26, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

qodo-merge-pro bot commented Jan 26, 2025

qodo-merge-pro bot commented Jan 26, 2025

qodo-merge-pro bot commented Jan 26, 2025

Fix #619 fix login #629

Fix #619 fix login #629

Conversation

Anchel123 commented Jan 26, 2025 • edited by qodo-merge-pro bot Loading

PR Type

Description

Changes walkthrough 📝

vercel bot commented Jan 26, 2025 • edited Loading

coderabbitai bot commented Jan 26, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

qodo-merge-pro bot commented Jan 26, 2025

PR Reviewer Guide 🔍

qodo-merge-pro bot commented Jan 26, 2025

PR Code Suggestions ✨

qodo-merge-pro bot commented Jan 26, 2025

CI Feedback 🧐

Anchel123 commented Jan 26, 2025 •

edited by qodo-merge-pro bot

Loading

vercel bot commented Jan 26, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)